Atari Mega Archive 1/Atari Mega Archive - Volume 1.iso/lists/gem/l_0799/549

Internet Message Format | 1994-08-27 | 2.5 KB

Date: Wed, 22 Jun 1994 22:06:39 -0400 (EDT)
From: Timothy Miller <[e-mail]>
Subject: Re: 20/06/94
To: [e-mail]
In-Reply-To: <[e-mail]>
Message-Id: <Pine.3.87.9406222239.A4885-0100000@grad>
Mime-Version: 1.0
Precedence: bulk


Waldi:

)>> I think we should make the standard so good that no-one will want
)>> to have a shortcut file.
)>
)> My point exactly.
)
)That's impossible. Keyboards are language specific.
)
)Typing ctrl-A accidently on a french keyboard is as likely as typing
)ctrl-Q accidently on a german or uk keyboard. If you were to have a
)french keyboard you would most likely start to argue about the danger
)of ctrl-Q.

This is true, but as most of us have agreed, quitting is important enough
to require confirmation.  Select-All, on the other hand would be annoying
to have to confirm.  Your arguement is invalid.


Mark H.

)>The big-cursor paradigm makes perfect sense.  The cursor is ALWAYS a
)>block, and vice versa.  If the cursor is big (a block), the contents are
)>deleted and the new information inserted in its place.
)
)What a totaly silly way to do work!

Actually, I think your way is even more silly, but let's not play
childish games.  There are merits to both.  In fact, this terminal
program that I'm using, ANSITerm, has an 'editor' (if you want to call it
that), and it uses ^B and ^E for block marking.  Now, considering that I
implemented it, I must have considered it to be a valid approach at the
time, and I still do.  I get along just fine marking blocks independant
of the cursor; however, I have also used the big-cursor approach and find
it to be no more technically superior, but certainly more efficient and
natural.  The block=cursor metaphor is a very effective and CONSISTENT
way of handling blocks, while your method requires the user to memorize
two keyypresses for every operation that would affect single characters
or blocks in a similar manner, not to mention extra ones to make up for
deficiencies in the system (like hide or deselect block).

If I can be reasonable about it, so can you.

)>)Yes, reOPEN realy tells the user exactly what is going to happen, in the
)>)same vain as 'save' and 'save as...'
)>
)>Yes, but REOPEN, to me, means 'open another copy of the same file',
)>rather than 'discard what's in memory and load the last saved version',
)>which is REVERT.
)
)I disagree.

Fine.  You disagree.  That doesn't really tell us much.  WHY do you
disagree?  The meanings of the words are not unclear, so what do you feel
is the problem?